 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA PM7384 FREEDM-84P672 REVISION B DEVICE ERRATA Issue 2 March 2000 PMC-Sierra, Inc. 105 - 8555 Baxter Place, Burnaby, BC Canada V5A 4V7 604 415 6000 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA TABLE OF CONTENTS 1. Introduction .......................................................................................................... 1 1.1. Device Identification .................................................................................. 1 1.2. Reference .................................................................................................. 1 FREEDM-84P672 Revision B Functional Deficiency List..................................... 2 2.1. PCICLK and SYSCLK can not be asynchronous ...................................... 3 2.2. Dropped data on unchannelised DS3 SBI SPE......................................... 4 2.3. TEMUX loss of frame may cause data corruption. .................................... 5 2.4. FREEDM registers cannot be accessed using fast back-to-back PCI transactions.......................................................................................................... 6 2.5. FREEDM may not generate PCI disconnect if host attempts a read multiple command which reads beyond register address 0xFFF. ........................ 7 2.6. FREEDM may under-report number of Transmit FIFO underrun events if two such events occur close together. ................................................................. 8 2.7. FREEDM may fail to Offset data as indicated in Receive Packet Descriptor. ............................................................................................................ 9 Documentation Errors ........................................................................................ 10 Contacting PMC-Sierra ...................................................................................... 11 2. 3. 4. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. i DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 1. Introduction In this document, Section 2 lists the known functional errata for revision B of PM7384 FREEDM-84P672 and Section 3 lists errors found in Issue 3 of the FREEDM-84P672 datasheet (PMC-1990114). 1.1. Device Identification The information contained in Section 2 relates to Revision B of PM7384 FREEDM84P672 only. The device revision code is marked at the end of the Wafer Batch Code on the face of the device (as shown in Figure 1.1). PM7384 FREEDM-84P672 Revision B is packaged in a 352-pin Ball Grid Array (SBGA). Figure 1.1: PM7384 FREEDM-84P672 Branding Format. Pin A1 Reference PMC Logo FREEDM Logo FREEDM 84P672 PM7384-BI-P C B Myyww TM Part Number Wafer Batch Code Assembly Date Code Not to Scale 1.2. * Reference PMC-1990114, FREEDM-84P672 Long Form Data Sheet, Issue 3. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 1 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2. FREEDM-84P672 Revision B Functional Deficiency List This section lists the known functional deficiencies for Revision B of FREEDM84P672 (as of the publication date of this document). For each deficiency, the known work-around and the operating constraints, with and without the work-around, are also described. Please report any functional deficiencies not covered in this document to PMC-Sierra. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 2 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.1. PCICLK and SYSCLK can not be asynchronous Description: The FREEDM-84P672 will not operate successfully if the rising edges of PCICLK are close to either rising or falling edges of SYSCLK. Through testing and simulation the specific failure conditions are predicted to be: * * The falling edge of SYSCLK precedes the rising edge of PCICLK by between 0.7 ns and 1.8 ns. The rising edge of SYSCLK occurs within 0.5 ns of the rising edge of PCICLK. If the two clocks are asynchronous these failure conditions will occur. This errata item will be corrected in Revision C. Workarounds: To ensure the failure regions are avoided, the SYSCLK and PCICLK should be kept synchronous, with some skew between the clock edges. This is most easily accomplished by tying the SYSCLK and PCICLKO pins together. The failure regions are both avoided due to the internal delay from PCICLK to PCICLKO. Note: When using a 66 MHz PCI bus, this workaround violates the maximum frequency specification for SYSCLK of 40 MHz. As a result, this workaround is only suitable for prototype testing, and can not be relied upon for production purposes. For the production part, the upper limit of SYSCLK (over process, temperature and voltage) is predicted to be approximately 45 MHz, the exact value is subject to device characterisation. Performance with workaround: FREEDM-84P672 works correctly. Performance without workaround: The FREEDM-84P672 will fail to process packets, due to internal timing conflicts. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 3 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.2. Dropped data on unchannelised DS3 SBI SPE. Description: When the TCAS672 block is configured to transmit a DS-3 on one of the SBI SPE's, there is a small probability that data bytes may be dropped from the transmit data stream. Workarounds: Carrying out the following procedure during configuration will eliminate this problem: 1. Place the SPE into T1 mode (SBI_MODE = 1 in register 440, 444 or 448 hex) 2. Wait at least 125 us 3. Place the SPE into DS-3 mode (SBI_MODE = 0 in register 440, 444 or 448 hex) Performance with workaround: With the extra configuration step, FREEDM-84P672 works correctly. Performance without workaround: Bytes of transmit data may be dropped during transfer to the SBI bus. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 4 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.3. TEMUX loss of frame may cause data corruption. Description: When a link on the TEMUX loses frame, corrupted pointer information may be sent over the SBI Bus to the FREEDM, resulting in data corruption on the FREEDM. When frame synchronization returns, the TEMUX will automatically recover and begin transmitting data to the FREEDM. However, due to the corrupted pointer information, the FREEDM may not recover and clear the data corruption in all cases. Workarounds: The links, and channels, affected by the loss of framing must be unprovisioned and then reprovisioned following recover of framing synchronization on the TEMUX. Performance with workaround: With the affected links unprovisioned then reprovisioned after each failure, the FREEDM-84P672 works correctly. Performance without workaround: The affected links may experience data corruption. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 5 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.4. FREEDM registers cannot be accessed using fast back-to-back PCI transactions. Description: The FREEDM-84P672 Registers cannot be read from or written to using a fast backto-back PCI transaction if the preceding PCI transaction also accessed the same FREEDM-84P672. This errata item will be corrected in Revision C. Workarounds: Configure the PCI system not to use fast back-to-back PCI transactions when writing to or reading from FREEDM-84P672. Performance with workaround: FREEDM-84P672 works correctly. Performance without workaround: FREEDM-84P672 registers may become corrupted and reads of registers may return incorrect values. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 6 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.5. FREEDM may not generate PCI disconnect if host attempts a read multiple command which reads beyond register address 0xFFF. Description: If a host incorrectly attempts a read multiple command whose address range spans beyond a point 4K bytes from the start of the FREEDM-84P672 register space, the FREEDM-84P672 may not issue a PCI disconnect and the PCI bus may hang. Workarounds: Ensure that the PCI host only accesses valid FREEDM-84P672 register addresses. Performance with workaround: FREEDM-84P672 works correctly. Performance without workaround: PCI bus may hang necessitating a system reset. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 7 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.6. FREEDM may under-report number of Transmit FIFO underrun events if two such events occur close together. Description: The FREEDM-84P672 reports underrun events on a per-channel basis to the host by setting bit STATUS[2] when a TDR is returned to the TDR Free Queue. If a packet underflows near the end of the packet and the next packet on the same channel underflows near the start of the packet, it is possible that only one TDR is returned to the TDR Free Queue with STATUS[2] set even though 2 underrun events occurred. Workarounds: None. Performance without workaround: Per channel underrun events can occasionally go unreported. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 8 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 2.7. FREEDM may fail to Offset data as indicated in Receive Packet Descriptor. Description: If a packet is received which spans more than one receive buffer and the size of any of the receive buffers is a multiple of the number of bytes being transferred across the PCI bus, the `Offset' and `Bytes in Buffer' fields may not be correctly written to the Receive Packet Descriptor (RPD) at the head of the buffer chain. The `offset' field may be erroneous set to zero and the `Bytes in Buffer' field may erroneously include the offset bytes in its count. This errata item will be corrected in Revision C. Workarounds: This failure can be avoided by setting the number of bytes of the PCI data transfer such that the size of the Partial Packet Buffer is not a multiple of the number of bytes of the PCI data transfer. For example: If Receive Packet Buffers of size 512 bytes are being used, set the XFER[3:0] of register 0x208 to a value such that the transfer size (16 * [XFER+1]) is not exactly divisible by 512 bytes. An XFER[3:0] value to 0xE, which equates to a transfer of 240 bytes, would avoid the errata. Performance with workaround: The situation causing the errata is avoided. The `offset' and `Bytes in Buffer' fields in the RPD are set correctly. Performance without workaround: The `offset' and `Bytes in Buffer' fields in the RPD may be set incorrectly and the host may interpret the result as if a number of bytes of invalid data were pre-pended to the packet. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 9 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 3. Documentation Errors This section lists the known documentation errors in Issue 3 of PMC-1990114 FREEDM-84P672 Datasheet. As of the publication date of this document, there are no known documentation errors. Please report any documentation errors not covered in this document to PMC-Sierra. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 10 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA 4. Contacting PMC-Sierra PMC-Sierra, Inc. 105 - 8555 Baxter Place Burnaby, BC V5A 4V7 Tel: (604) 415-6000 Fax: (604) 415-6200 Product Marketing Manager: e-mail: Direct Line: Product information: Applications information: Internet: Trevor Nonay trevor_nonay@pmc-sierra.com (604) 415-6163 info@pmc-sierra.bc.ca apps@pmc-sierra.bc.ca http://www.pmc-sierra.com PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC. 11 DATASHEET ERRATA PM7384 FREEDM-84P672 PMC-200-0051 ISSUE 2 FREEDM-84P672 REVISION A DEVICE ERRATA NOTES Seller will have no obligation or liability in respect of defects or damage caused by unauthorized use, mis-use, accident, external cause, installation error, or normal wear and tear. There are no warranties, representations or guarantees of any kind, either express or implied by law or custom, regarding the product or its performance, including those regarding quality, merchantability, fitness for purpose, condition, design, title, infringement of thirdparty rights, or conformance with sample. Seller shall not be responsible for any loss or damage of whatever nature resulting from the use of, or reliance upon, the information contained in this document. In no event will Seller be liable to Buyer or to any other party for loss of profits, loss of savings, or punitive, exemplary, incidental, consequential or special damages, even if Seller has knowledge of the possibility of such potential loss or damage and even if caused by Seller's negligence. (c) 2000 PMC-Sierra, Inc. Issue date: January, 2000 Printed in Canada PMC-Sierra, Inc. 105 - 8555 Baxter Place Burnaby, BC Canada V5A 4V7 604 415 6000 |
Price & Availability of 200005
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |